Problem Note 68336: SAS® Deployment Manager fails with "groovy.lang.MissingMethodException: No signature of method" error during SAS® Web Application Server Configuration
 |  |  |  |  |
SAS Deployment Manager fails during SAS Web Application Server configuration with the following error:
.......................
.......................
Caused by: groovy.lang.MissingMethodException: No signature of method: static com.sas.appserver.utils.ConfigFileAccessHelper.updateSetenvFile() is applicable for argument types: (java.io.File, java.io.File, java.util.HashSet, java.util.HashMap, com.sas.appserver.utils.OsType) values: {/sas/config/Lev1/Web/WebAppServer/Backup/SASServer1_1.<date_timestamp>/bin/setenv.sh, /sas/config/Lev1/Web/WebAppServer/SASServer1_1/bin/setenv.sh, [sas.scs.svc.port, sas.scs.cas.host, sas.scs.svc.host, sas.scs.cas.scheme, sas.scs.cas.port, sas.scs.svc.internal, sas.scs.svc.scheme], ["sas.retry.internal.url":"true", "sas.web.html.cdps.use.internal.urls":"true"], unx}
This error occurs when you have a reverse proxy or a load balancer configured for the middle tier and are doing one of the following:
- an update in place
- the Update Existing Configuration task
This issue has been addressed in SAS 9.4 Rev. 940_21w26. To resolve this issue, you need to either use a release prior to SAS 9.4 Rev. 940_20w47 or after SAS 9.4 Rev. 940_21w26. You can find the release number from your Software Order Confirmation Email, such as Rev. 940_21w17.
In any case, if you cannot obtain a newer release as listed above, then complete the following workaround.
The procedure to install this fix is to replace the existing JAR file with a new one:
- Find the sas.appserver.config.jar file in an existing SAS installation in SASHome, which is typically similar to this: <SASHome>/SASDeploymentManager/9.4/products/deploywiz__94564__prt__xx__sp0__1/deploywiz/appserver
Note that the example is a Linux directory, but Windows has the same directory structure. The 94564 number might change based on your deployment.
- Rename the existing JAR file and move this JAR file to a different directory. The new name is not important, but you can use:
sas.appserver.config.jar.ORIGINAL
- Download the new JAR file from the Downloads tab of this SAS Note, name it sas.appserver.config.jar, and then copy the new JAR file into the directory.
- In addition to SASHome, if a SAS Install Depot is in use, then the same file within the depot should be replaced as well. In a SAS depot, the file can be found in a directory similar to the following:
<Depot>/products/deploywiz__94564__prt__xx__sp0__1/deploywiz/appserver
- Use the same process for the depot as well: rename/move the existing file into another directory, and then copy the new JAR file into the depot directory.
- Click Retry in the SAS Deployment Manager error window.
Note: The sas.appserver.config.jar file provided on the Downloads tab is the same for both Windows and Linux/UNIX environments.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Application Server | Solaris for x64 | 9.46 | 9.46 | 9.4 TS1M7 | 9.4 TS1M7 |
| Linux for x64 | 9.46 | 9.46 | 9.4 TS1M7 | 9.4 TS1M7 | ||
| HP-UX IPF | 9.46 | 9.46 | 9.4 TS1M7 | 9.4 TS1M7 | ||
| 64-bit Enabled Solaris | 9.46 | 9.46 | 9.4 TS1M7 | 9.4 TS1M7 | ||
| 64-bit Enabled AIX | 9.46 | 9.46 | 9.4 TS1M7 | 9.4 TS1M7 | ||
| Microsoft® Windows® for x64 | 9.46 | 9.46 | 9.4 TS1M7 | 9.4 TS1M7 | ||